Method and apparatus for providing mobile device information through a computing device

ABSTRACT

Methods and apparatuses for a service system capable of providing, to a computing device, mobile device information received from a mobile device, the mobile device being associated with a user of the computing device, are described herein. In one embodiment, the mobile device, service system, and computing device may each be separate and distinct from the others. In various embodiments, the client device may facilitate a user in viewing and/or interacting with the provided mobile device information.

RELATED APPLICATIONS

The present application claims priority to U.S. Provisional Application60/828,919, entitled “Mobile Phone Interacting Method and Apparatus”,filed on Oct. 10, 2006. The specifications of the 60/828,919 provisionalapplication is hereby fully incorporated by reference.

TECHNICAL FIELD

Embodiments of the present invention relate generally to mobile devicesand services. More specifically, the embodiments relate to a service forproviding access to and interaction with mobile device information froma computing device.

BACKGROUND

Wireless phones have a variety of functionalities that customers caninteract with. Such functionalities include making phone calls, sendingmessages, accessing call history, browsing network content, and takingand viewing photos and videos. On some smartphone devices (mini-PCs inthe form of a phone), there are thousands of applications and servicesthat enable new functionalities.

Wireless phones are typically designed for mobile usage, and thereforehave a small form factor, including small display screens, smallkeypads, typically access to only one function at a time, and so forth.

Many phones today are capable of syncing with a PC and/or server totransfer personal information management (PIM) content (email, calendar,contacts, tasks) and, in some cases, photos and music while connectedvia USB or wireless connection for storage on the PC.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention will be described by way ofexemplary embodiments, but not limitations, illustrated in theaccompanying drawings in which like references denote similar elements,and in which:

FIG. 1 is an overview of various embodiments of the present invention;

FIG. 2 illustrates a flow chart view of selected service systemoperations of the methods of various embodiments of the presentinvention;

FIG. 3 illustrates a flow chart view of selected computing deviceoperations of the methods of various embodiments of the presentinvention;

FIG. 4 illustrates an exemplary display of computing device inaccordance with various embodiments of the invention; and

FIG. 5 illustrates an example computer system suitable for use topractice service system and/or computing device aspects of variousembodiments of the present invention.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Illustrative embodiments of the present invention include, but are notlimited to, methods and apparatuses for a service system capable ofproviding, to a computing device, mobile device information receivedfrom a mobile device, the mobile device being associated with a user ofthe computing device. In some embodiments, the mobile device, servicesystem, and computing device may each be separate and distinct from theothers. The service system may also receive an indication, from thecomputing device, of a user interaction. In response, the service systemmay update the mobile device information, perform an action on behalf ofthe mobile device, or direct the mobile device to perform the action. Invarious embodiments, the client device may facilitate a user in viewingand/or interacting with the provided mobile device information. Theclient device may further receive one or more user interactions andprovide service system with an indication of the interaction(s).

Various aspects of the illustrative embodiments will be described usingterms commonly employed by those skilled in the art to convey thesubstance of their work to others skilled in the art. However, it willbe apparent to those skilled in the art that alternate embodiments maybe practiced with only some of the described aspects. For purposes ofexplanation, specific numbers, materials, and configurations are setforth in order to provide a thorough understanding of the illustrativeembodiments. However, it will be apparent to one skilled in the art thatalternate embodiments may be practiced without the specific details. Inother instances, well-known features are omitted or simplified in ordernot to obscure the illustrative embodiments.

Further, various operations will be described as multiple discreteoperations, in turn, in a manner that is most helpful in understandingthe illustrative embodiments; however, the order of description shouldnot be construed as to imply that these operations are necessarily orderdependent. In particular, these operations need not be performed in theorder of presentation.

The phrase “in one embodiment” is used repeatedly. The phrase generallydoes not refer to the same embodiment; however, it may. The terms“comprising,” “having,” and “including” are synonymous, unless thecontext dictates otherwise. The phrase “A/B” means “A or B”. The phrase“A and/or B” means “(A), (B), or (A and B)”. The phrase “at least one ofA, B and C” means “(A), (B), (C), (A and B), (A and C), (B and C) or (A,B and C)”. The phrase “(A) B” means “(B) or (A B)”, that is, A isoptional.

FIG. 1 illustrates an overview of various embodiments of the presentinvention. As illustrated, service system 108 may include a service 110and a database 112. In some embodiments, service system 108 may compriseone or more computing devices, each having at least a portion of service110 and/or database 112. Service 110 may be capable of providing mobiledevice clients 104 to a plurality of mobile devices 102 via networkingfabric 106. In various embodiments, the mobile device clients 104 may becapable of providing mobile device information of mobile devices 102 toservice 110 and of receiving, in return, notification of updates to themobile device information or of the performance of any actions byservice 110 on behalf of mobile devices 102. In one embodiment, mobiledevice client 104 may receive a directive from service 110 to perform anaction.

In various embodiments, the updates and actions may be the result ofinteractions with the mobile device information by a user of computingdevice 116. As shown, service 110 may provide the received mobile deviceinformation to computing device 116 via networking fabric 114 to enablea user of computing device 116 to view and/or interact with the mobiledevice information. In one embodiment, the user may be associated with amobile device 102 and service 110 may require authentication of the userbefore providing the mobile device information of the user-associatedmobile device 102. Service 110 may then receive one or more indicationsof user interaction with the mobile device information from computingdevice 116. In response, service 110 may update the mobile deviceinformation, perform an action on behalf of the mobile device 102, ordirect the mobile device 102 to perform the action. In variousembodiments, networking fabric 114 may be the same, in totality or inpart, as networking fabric 106.

In some embodiments, computing device 116 may include logic 118 capableof receiving the mobile device information, facilitating the user inviewing and/or interacting with the information, receiving one or moreuser interactions, and providing an indication of the interaction(s) toservice 110. In one embodiment, logic 118 may be a plug-in to a browserapplication of computing device 116.

As illustrated, mobile devices 102 may be any sort of mobile devicesknown in the art, except for mobile device client 104. Mobile devices102 may be wireless mobile phones, personal digital assistants (PDA),palm computers, or media players. Such mobile devices 102 may have asmall form factor and a reduced set of inputs, in some embodiments.Also, mobile devices 102 may have one or more wired, wireless, infrared,etc. networking interfaces to facilitate communication with servicesystem 108 via networking fabric 106. In other words, networking fabric106 may comprise a wired, wireless or infrared based access point, andthe fabric may comprise wired, wireless and/or infraredsegments/domains.

As mention above, each mobile device 102 may include or receive mobiledevice client 104, which may be any single- or multi-threaded clientapplication. Mobile device clients 104 may be received from service 110via networking fabric 106 or may come installed with other applicationsof mobile device 102. In some embodiments, mobile device client 104 maybe provided in response to a mobile device 102 user registering for aservice. In one embodiment, mobile device client 104 may include anapplication programming interface (API) with a plurality of functionscallable by service 110. Mobile device client 104 may also include logicto periodically provide mobile device information, such as emails,messages, a call history, photos, music, videos, a calendar, and mobiledevice settings, to service 110. In one embodiment, logic of mobiledevice client 104 may monitor for changes to mobile device information,such as a new email sent by mobile device 102, and may provide inresponse updated mobile device information to service 110. Also, in suchan embodiment, the logic may simply provide information indicate of thechanges, such as the adding of a new contact, rather than re-providingall mobile device information each time any part of it is updated. Insome embodiments, mobile device client 104 may provide the mobile deviceinformation in real time or in batches.

In various embodiments, the API of mobile device client 104 may beconfigured to hook into native APIs of mobile device 102. For example,the API of mobile device client 104 may include a callable functioncapable of causing a text message to be sent. That callable function mayin turn call an API function of a native text messaging application ofmobile device 102. Also, the API of mobile device client 104 maycomprise modules corresponding to native applications and/or features ofmobile device 102, such as Short Message Service (SMS)/MultimediaMessaging Service (MMS) messages, calls, photos, videos, contacts,files, events, voicemail, lists, ring tones, themes, speed dial, alarmclock, music, phone settings, battery life, and third party components,among many others. In some embodiments, service 110 may direct mobiledevice 102 to perform an action by calling a function of the API ofmobile device client 104. Such actions may include initiating a call,such as a Voice over IP (VoIP) call, sending an email, posting a photoor video for sharing, sending a text message, or changing a mobiledevice setting. In further embodiments, service 110 may also notifymobile device client 104 that the mobile device information has beenupdated or that service 110 has performed an action on behalf of mobiledevice 102, and such notification may be provided by calling a functionof the API of mobile device client 104.

In some embodiments, service 110 may store a variety of mobile deviceclients 104, each mobile device client 104 customized for a differentmobile device 102 platform. For example, mobile device client 104 may becustomized for a Windows mobile platform, a Symbian platform, a J2MEplatform, a BREW platform, or a Linux platform, among many others.

As illustrated, service system 108 may include one or more of anysingle- or multi-processor or processor core central processing unit(CPU) computing system, and computing device 116 may be any single- ormulti-processor or processor core central processing unit (CPU)computing system. Service System 108 may include and computing device116 may be a personal computer (PC), a workstation, a server, a router,a mainframe, a modular computer within a blade server or high-densityserver, a personal digital assistant (PDA), an entertainment center, aset-top box, or a mobile device. Also, each computer system of servicesystem 108 and computing device 116 may each be capable of operating aplurality of operating systems (OS) in a plurality of virtual machines(VM) using virtualization technologies. An exemplarysingle-/multi-processor or processor core computing system of each ofservice system 108 and computing device 116 is illustrated by FIG. 5,and is described in greater detail below. Hereinafter, including in theclaims, processor and processor core shall be used interchangeable, witheach term including the other.

As is further shown, mobile devices 102 and service system 108 may beconnected by a networking fabric 106, and service system 108 andcomputing device 116 may be connected by a networking fabric 114. In oneembodiment, networking fabric 106 and networking fabric 114, asdescribed earlier, may be the same, partially the same, or a differentnetworking fabric. Networking fabric 106 and networking fabric 114 mayeach be any sort of networking fabric known in the art, such as one ormore of a local area network (LAN), a wide area network (WAN), a Wi-Finetwork, a personal area network (PAN), and the Internet. In variousembodiments, one or both of networking fabrics 106 and 114 may compriseprivate network(s) of enterprise(s). The parties to the connections,here mobile devices 102, service system 108, and computing devices 116,may further use any communication protocol known in the art, such as theHypertext Transfer Protocol (HTTP), and any transport protocol known inthe art, such as the Transmission Control Protocol/Internet Protocol(TCP/IP) suite of protocols. As mentioned, each of mobile devices 102,service system 108, and computing devices 116 may have at least onenetworking interface to facilitate networked communication across eitheror both of networking fabric 106 and 114.

As illustrated and described above, service system 108 may includeservice 110, which may be any single- or multi-threaded serviceapplication and may be capable of simultaneously serving multiple mobiledevices 102 and computing devices 116. In some embodiments, service 110may comprise a plurality of servers, such as one or more web servers, apush server for providing notifications/updates, a proxy server forreceiving mobile device information and notifications, and one or moreapplication servers, such as a messaging server, to perform actions onbehalf of mobile devices 102.

In various embodiments, service 110 may facilitate users having mobiledevices 102 in registering for services provided by service system 108through service 110. Service 110 may ask users for a login name and apassword, as well as other information useful for authentication, andmay store the information in database 112. Service 110 may also askusers for information regarding mobile devices 102. In some embodiments,mobile devices 102 may have come with mobile device clients 104preinstalled, and service 110 may use the phone information receivedfrom the user to recognize and/or activate the mobile devices 102. Inother embodiments, upon registering and providing phone information,service 110 may provide a mobile device client 104 to the mobile device102 corresponding to the phone information. In such embodiments, themobile device client 104 may be provided to the mobile device 102 viathe networking fabric 106. And as mentioned above, mobile device client104 may be targeted for mobile device 102's platform.

As mentioned above, service 110 may automatically receive mobile deviceinformation from mobile device clients 104, either in real time or inbatches reflecting changes or additions to mobile device information.Upon receiving mobile device information from a mobile device client104, service 110 may store the information in database 112.

In various embodiments, when a registered user desires to view and/orinteract with mobile device information of the user's mobile device 102,the user may authenticate with service 110, which may requireauthentication before providing mobile device information. Service 110may present an authentication web page to a user browsing on a computingdevice 116 to facilitate the user in authenticating. The web page mayinclude, for example, text input fields for a login name and a password,as well as a submit button. Service 110 may then receive a login nameand password submitted by the user and may compare that information to alogin name and password stored in database 112. If the comparison doesnot indicate a match, service 110 may notify the user of anauthentication failure.

If the comparison does indicate a match, however, service 110 mayproceed and provide a customized web page or other display including themobile device information to the computing device 116 of theauthenticated user. In some embodiments, the customized web page orother display may provide the mobile device information in a formatcomprehensible by logic 118 or a browser application of the computingdevice 116 to enable the computing device 116 to display the mobiledevice information to the user for the user to view and/or interactwith. For example, the provided web page/displayed may be a HypertextMarkup Language (HTML), an Extensible Markup Language (XML), and/or aJavaScript document.

In various embodiments, service 110 may receive from computing device116 an indication of one or more user interactions with the providedmobile device information. The indication may also comprise an HTML orXML document, but may have any format known in the art. Further, theinteractions conveyed by the indication may be one or more of an updateto the mobile device information or a request for the performance of anaction by or on behalf of mobile device 102.

If the interaction(s) include an update to the mobile deviceinformation, such as a change of a phone setting or a new contact,service 110 may store the updated mobile device information in database112 and notify mobile device 102 of the update, in one embodiment bycalling functions of the above-described mobile device client 104 API.If the interaction(s) include a request for the performance of an actionby or on behalf of mobile device 102, service 110 may either perform theaction on behalf of mobile device 102 or may direct mobile device 102 toperform the action. In one embodiment, service 110 may direct mobiledevice 102 to perform the action, if mobile device 102 is reachable vianetworking fabric 106, or may perform the action itself on behalf ofmobile device 102 if mobile device 102 is unreachable. In suchembodiments, service 110 may direct mobile device 102 to perform theaction by calling functions of the mobile device client API, asdescribed above. Service 110 may perform the action on behalf of mobiledevice 102 via application servers of service 110. For example, if theaction is the sending of a text message, service 110 may send the textmessage via a messaging application server of service 110. Service 110may then notify mobile device 102 of the performance of the action onits behalf by calling a function of the mobile device client 104 API, inone embodiment causing the mobile device 102 to believe that mobiledevice 102, rather than service 110, performed the action.

As is shown, service system 108 may include database 112, and database112 may be any sort of database known in the art, except for itsinternal structuring (e.g., tables) and data. Database 112 may be arelational database, a normalized database, a de-normalized database, ora file. In various embodiments, database 112 may store versions ofmobile device client 104 targeted to a number of mobile deviceplatforms, as described above. Database 112 may further store mobiledevice information for each mobile device 102 as well as associatedauthentication information, such as a login name and a password, whichmay be used by service 110 to authenticate users of computing devices116.

In various embodiments, as mentioned above, a computing device 116 mayinclude logic 118. Logic 118 may comprise any sort of single- ormulti-thread application and, as mentioned above, may be implemented asa plug-in to a computing device 116 browser, such as a plug-in to aMozilla Firefox browser, or as Active-X component(s). In otherembodiments, logic 118 may instead be implemented as a separate,stand-alone program invocable by a user. In yet other embodiments,computing device 116 may not include logic 118, and the browserapplication may serve as the point of interaction between service 110and the user.

In some embodiments, computing device 116 may facilitate a user inauthenticating with service 110, as described above in greater detail.Upon authentication of the user, computing device 116 may receive mobiledevice information and may, in response, render a visual display of themobile device information. Such an exemplary display is illustrated byFIG. 4 and is described in greater detail below. As shown in FIG. 4, thedisplay may comprise a dashboard like layout having regions of thedisplay associated with categories of mobile device information. Eachregion may comprise a content and/or functionality module. In oneembodiment, the regions/modules may be added, removed, or rearranged bythe user. In some embodiments, modules for viewing, managing, and usingone or more of SMS/MMS messages, calls, photos, videos, contacts, files,events, voicemail, lists, ring tones, themes, speed dial, alarm clock,music, phone settings/rules, battery life, and/or third party componentsmay be included in the rendered display. The modules may also include asystem module for handling communication with service 110. In someembodiments, the rendered display may differ from that provided bymobile device 102.

In various embodiments, the modules may facilitate the user in viewingand interacting with the rendered mobile device information. Forexample, the modules may facilitate the user in viewing SMS/MMS inboxcontent, sending responses or create new SMS/MMS messages, saving mobiledevice 102 sent or received messages locally to computing device 102,viewing call history, making VoIP calls, seeing photos and videos takenby mobile device 102, posting photos and videos to sharing sites, andsetting rules/preferences/settings of mobile device 102. To providefacilities for such interactions, the modules may include form elementsand other graphic elements capable of receiving and registering userinput(s). In other embodiments, one or more of the modules may simplydisplay mobile device information and may provide a control whoseactuation results in the opening of a new input display window. Uponreceiving and registering user interaction(s), logic 118 may provide anindication of the interactions to service 110.

In some embodiments, users who communicate with one another via call ormessage and who also use service 110 have the option to have informationpresented to their contacts automatically, like what kind of phone theyhave, how they have personalized it thru service 110, what type ofphones their friends are using, new media they have captured, andpurchases they have made. Users may effectuate this option through oneor more settings of mobile device 102 associated with the automaticpresentation of information to contacts.

FIG. 2 illustrates a flow chart view of selected service systemoperations of the methods of various embodiments of the presentinvention. As illustrated, a service system may provide a mobile deviceclient to a mobile device to facilitate the mobile device in providingmobile device information of the mobile device to the service system,block 202. The service system and mobile device may be separate anddistinct from each other. In one embodiment, the mobile deviceinformation includes at least one of emails, messages, a call history,photos, music, videos, a calendar, and mobile device settings.Subsequently, the service system may receive the mobile deviceinformation from the mobile device, block 204.

In various embodiments, the service system may then requireauthentication of a user of a computing device before providing themobile device information to the computing device, block 206. Theservice system and computing device may be separate and distinct fromeach other. And in some embodiments, the user may be associated with themobile device. Upon receiving authentication, the service system mayprovide the mobile device information to the computing device tofacilitate the user in viewing and/or interacting with the mobile deviceinformation, block 208.

As is further shown, the service system may then receive from thecomputing device an indication of one or more user interactions with themobile device information, block 210. In response, the service systemmay update the mobile device information, block 212, perform an actionon behalf of the mobile device, block 214, or direct the mobile deviceto perform the action, block 216. In one embodiment, the action is oneor more of initiating a Voice over IP (VoIP) call, sending an email,posting a photo or video for sharing, sending a text message, orchanging a mobile device setting. In some embodiments, the servicesystem may then notify the mobile device of the updated mobile deviceinformation or the performed action, block 218. The service system maythen receive, in response, updated mobile device information from themobile device, block 204.

FIG. 3 illustrates a flow chart view of selected computing deviceoperations of the methods of various embodiments of the presentinvention. As illustrated, a computing device may receive mobile deviceinformation from a service system, block 302, the mobile deviceinformation having been provided to the service system by a mobiledevice associated with a user of the computing device, the mobiledevice, service system, and computing device each being separate anddistinct from the others. In one embodiment, the mobile deviceinformation may include at least one of emails, messages, a callhistory, photos, music, videos, a calendar, and mobile device settings.The computing device may then facilitate the user in viewing and/orinteracting with the mobile device information, block 304. In oneembodiment, the facilitating may include providing a user interfacehaving icons/glyphs associated with modules for handling differentcategories of the mobile device information. In various embodiments, thecomputing device may then receive one or more user interactions with themobile device information, block 306, and, in response, may provide anindication of the one or more interactions to the server system, block308. In one embodiment, at least one of the receiving, the facilitating,the receiving, and the providing is performed by a plug-in to a browserof the computing device.

FIG. 4 illustrates an exemplary display of a computing device inaccordance with various embodiments of the invention. As illustrated, adisplay of a computing device may present to a user a plurality of iconsor glyphs corresponding to categories of mobile device information, suchas a user photo, voice mail, photos, videos, messages, call history, acalendar, and phone rules/settings, among others. Each icon/glyph mayoccupy a specific region of the display, or may be added and removedfrom the display in response to user interactions. As described above ingreater detail with regard to FIG. 1, each icon/glyph may be associatedwith one or more modules configured to cooperate with each other toconvey mobile device information for viewing by the user, and may alsobe configured to include mechanisms to facilitate user interaction, suchas editable text boxes, various form controls, and graphic buttons orkeys whose actuation may result in the creation of a new window, such asa text message window. The exemplary display is provided simply for thesake of illustration. The categories of information and their visualconfiguration may vary from embodiment to embodiment.

FIG. 5 illustrates an example computer system suitable for use topractice service system and/or computing device aspects of variousembodiments of the present invention. As shown, computing system 500includes a number of processors or processor cores 502, and systemmemory 504. For the purpose of this application, including the claims,the terms “processor” and “processor cores” may be consideredsynonymous, unless the context clearly requires otherwise. Additionally,computing system 500 includes mass storage devices 506 (such asdiskette, hard drive, compact disc read only memory (CDROM) and soforth), input/output devices 508 (such as display, keyboard, cursorcontrol and so forth) and communication interfaces 510 (such as networkinterface cards, modems and so forth). The elements are coupled to eachother via system bus 512, which represents one or more buses. In thecase of multiple buses, they are bridged by one or more bus bridges (notshown).

Each of these elements performs its conventional functions known in theart. In particular, system memory 504 and mass storage 506 may beemployed to store a working copy and a permanent copy of the programminginstructions implementing at least a portion of one of the variouscomponents, such as service 110 or logic 118, herein collectivelydenoted as 522. The various components may be implemented by assemblerinstructions supported by processor(s) 502 or high-level languages, suchas, for example, C, that can be compiled into such instructions.

The permanent copy of the programming instructions may be placed intopermanent storage 506 in the factory, or in the field, through, forexample, a distribution medium (not shown), such as a compact disc (CD),or through communication interface 510 (from a distribution server (notshown)). That is, one or more distribution media having animplementation of the agent program may be employed to distribute theagent and program various computing devices.

The constitution of these elements 502-512 are known, and accordinglywill not be further described.

Although specific embodiments have been illustrated and describedherein, it will be appreciated by those of ordinary skill in the artthat a wide variety of alternate and/or equivalent implementations maybe substituted for the specific embodiments shown and described, withoutdeparting from the scope of the embodiments of the present invention.This application is intended to cover any adaptations or variations ofthe embodiments discussed herein. Therefore, it is manifestly intendedthat the embodiments of the present invention be limited only by theclaims and the equivalents thereof.

What is claimed is:
 1. A method comprising: receiving, by a servicesystem, from a mobile device, mobile device information of the mobiledevice, wherein the mobile device information was sent to the servicesystem in response to the mobile device information being changed on themobile device, wherein the mobile device information was sent to enablea user of the mobile device to view or interact with the mobile deviceinformation using a computing device, and to perform an action towardsanother computing device on behalf of the mobile device, throughinteraction with the mobile device information, using the computingdevice and the service system, and wherein the mobile device, theservice system, the computing device, and the other computing device areseparate and distinct from each other; providing, by the service system,the mobile device information to the computing device, for the user toview or interact with the mobile device information; receiving from thecomputing device, by the service system, an indication of one or moreuser interactions with the mobile device information; and performing onbehalf of the mobile device, by the service system, in response toreceipt of the indication from the computing device, an action towardsthe other computing device, based at least in part on the receivedindication of one or more user interactions.
 2. The method of claim 1,wherein the mobile device information includes at least one of emails,messages, a call history, photos, music, videos, a calendar, and mobiledevice settings.
 3. The method of claim 1, further comprising requiring,by the service system, authentication of the user before performing saidproviding.
 4. The method of claim 1, wherein the action is one or moreof initiating a Voice over IP (VoIP) call, sending an email, posting aphoto or video for sharing, or sending a text message, on behalf of themobile device.
 5. The method of claim 1, further comprising, inresponse, updating, by the service system, the mobile device informationon the mobile device, or directing, by the service system, the mobiledevice to perform an action.
 6. The method of claim 5, wherein theaction further includes one or more of initiating a VoIP call, sendingan email, posting a photo or video for sharing, sending a text message,or changing a mobile device setting.
 7. The method of claim 1, furthercomprising providing, by the service system, a mobile device client tothe mobile device to facilitate the mobile device in providing themobile device information to the service system.
 8. A service systemcomprising: one or more processors; and a service to be operated by theone or more processors to: provide, to a computing device, mobile deviceinformation of a mobile device for a user to view or interact with themobile device information, wherein the mobile device information isprovided to the service system, from the mobile device, in response tothe mobile device information being changed on the mobile device,wherein the mobile device information was sent to enable the user of amobile device to view or interact with the mobile device informationusing a computing device, and to perform an action towards anothercomputing device on behalf of the mobile device, through interactionwith the mobile device information, using the computing device and theservice system, and wherein the mobile device, the service system, thecomputing device, and the other computing device are separate anddistinct from each other; receive, from the computing device, anindication of one or more user interactions with the mobile deviceinformation; and in response to receipt of the indication from thecomputing device of one or more user interactions, perform an actiontowards the other computing device by the service system on behalf ofthe mobile device.
 9. The service system of claim 8, wherein the mobiledevice information includes at least one of emails, messages, a callhistory, photos, music, videos, a calendar, and mobile device settings.10. The service system of claim 8, wherein the service is further to beoperated to require authentication of the user before performing saidprovide.
 11. The service system of claim 8, wherein the service isfurther to be operated to notify the mobile device of the performedaction.
 12. The service system of claim 8, wherein the action includesone or more of initiating a Voice over IP (VoIP) call, sending an email,posting a photo or video for sharing, or sending a text message.
 13. Theservice system of claim 8, wherein the service is further to be operatedto direct the mobile device to perform an action including one or moreof initiating a Voice over IP (VoIP) call, sending an email, posting aphoto or video for sharing, sending a text message, or changing a mobiledevice setting.
 14. The service system of claim 8, wherein the serviceis further to provide a mobile device client to the mobile device tofacilitate the mobile device in providing the mobile device informationto the service system.
 15. A method comprising: receiving, by acomputing device, from a service system, mobile device information of amobile device, wherein the mobile device information was provided to theservice system, from the mobile device, in response to the mobile deviceinformation being changed on the mobile device, wherein the mobiledevice information was sent to enable a user of the mobile device toview or interact with the mobile device information using the computingdevice, and to perform an action towards another computing device onbehalf of the mobile device, through interaction with the mobile deviceinformation, using the computing device and the service system, andwherein the mobile device, the service system, the computing device, andthe other computing device are separate and distinct from each other;facilitating, by the computing device, for the user to view or interactwith the mobile device information; receiving, by the computing device,one or more user interactions with the mobile device information; and inresponse to, providing, by the computing device, receipt of anindication of the one or more interactions to the service system for theservice system to perform an action towards the other computing deviceby the service system on behalf of the mobile device.
 16. The method ofclaim 15, wherein at least one of said receiving, said facilitating,said receiving, and said providing is performed by a plug-in to abrowser of the computing device.
 17. The method of claim 15, wherein themobile device information includes at least one of emails, messages, acall history, photos, music, videos, a calendar, and mobile devicesettings.
 18. The method of claim 15, wherein the facilitating includesproviding, by the computing device, a user interface having icons/glyphsassociated with modules for handling different categories of the mobiledevice information.